Release 10.1A: OpenEdge Development:
Debugging and Troubleshooting

Understanding Web service information in WSA logs

When the WSA starts up, each WSA instance receives a unique, alphanumeric identifier called the WSA ID. The WSA ID appears in the log file after the “ID”:

ID f83c04d3ca9b076a:648016:1067934305:-7fff

When the WSA instance receives a request from a Web service, the WSA instance assigns the request a unique alphanumeric identifier called request ID. When the WSA instance logs information about a Web service request, the WSA includes the request ID in the following format, where wsaid-value is the WSA ID and reqid-value is the request ID:

(reqid:wsaid-value#reqid-value)

The client uses the WSA ID and the request ID to find more detailed information in the corresponding entries of the WSA log file.

The following log (with headers suppressed) was generated for WSADefault entry type at logging level 2(Basic).

1 wsa1 Starting WSA adapter wsa1, version 10.1A1) ID f83c04d3ca9b076a:648016:1067934305:-7fff (10620) 1 wsa1 Runtime properties set for WSA 2 wsa1 Admin-Provider Deploying Web Service application: GetCustName GetCustName 4GL-Provider    Error in SOAP request exectuion: Connect Fauilure: Application Service GetCustName Unknown at NameServer at Host localhost Port 5162. (8234) (10926)

For more information on Web Services Adapter logging see OpenEdge Development: Web Services .

For more information on using the wsaman utility, see OpenEdge Application Server: Administration . For more information on the serviceLoggingLevel and serviceFaultLevel properties, see the Web service properties reference sections of OpenEdge Application Server: Administration .